-
Notifications
You must be signed in to change notification settings - Fork 0
fix(deps): update dependency axios to v0.30.0 [security] #106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
8111837
to
78969e5
Compare
78969e5
to
0644411
Compare
0644411
to
5d1bb87
Compare
5d1bb87
to
d50a466
Compare
|
d50a466
to
2a665c7
Compare
2a665c7
to
4e300b7
Compare
4e300b7
to
dd60403
Compare
This PR contains the following updates:
0.26.1
->0.30.0
GitHub Vulnerability Alerts
CVE-2023-45857
An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.
CVE-2025-27152
Summary
A previously reported issue in axios demonstrated that using protocol-relative URLs could lead to SSRF (Server-Side Request Forgery).
Reference: axios/axios#6463
A similar problem that occurs when passing absolute URLs rather than protocol-relative URLs to axios has been identified. Even if
baseURL
is set, axios sends the request to the specified absolute URL, potentially causing SSRF and credential leakage. This issue impacts both server-side and client-side usage of axios.Details
Consider the following code snippet:
In this example, the request is sent to
http://attacker.test/
instead of thebaseURL
. As a result, the domain owner ofattacker.test
would receive theX-API-KEY
included in the request headers.It is recommended that:
baseURL
is set, passing an absolute URL such ashttp://attacker.test/
toget()
should not ignorebaseURL
.baseURL
with the user-provided parameter), axios should verify that the resulting URL still begins with the expectedbaseURL
.PoC
Follow the steps below to reproduce the issue:
Even though
baseURL
is set tohttp://localhost:10001/
, axios sends the request tohttp://localhost:10002/
.Impact
baseURL
and does not validate path parameters is affected by this issue.Release Notes
axios/axios (axios)
v0.30.0
Compare Source
Release notes:
Bug Fixes
Contributors to this release
Full Changelog: axios/axios@v0.29.0...v0.30.0
v0.29.0
Compare Source
Release notes:
Bug Fixes
Contributors to this release
v0.28.1
Compare Source
Release notes:
Release notes:
Bug Fixes
req
is not defined (#6307)v0.28.0
Compare Source
Release notes:
Bug Fixes
withXSRFToken
option to v0.x (#6091)Backports from v1.x:
axios.formToJSON
method (#4735)url-encoded-form
serializer to respect theformSerializer
config (#4721)string[]
toAxiosRequestHeaders
type (#4322)AxiosError
stack capturing; (#4718)AxiosError
status code type; (#4717)blob
to the list of protocols supported by the browser (#4678)v0.27.2
Compare Source
Fixes and Functionality:
v0.27.1
Compare Source
Fixes and Functionality:
v0.27.0
Compare Source
Breaking changes:
Content-Type
request header when passing FormData (#3785)transformRequest
andtoFormData
(#4470)QOL and DevX improvements:
Fixes and Functionality:
Internal and Tests:
Documentation:
Notes:
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.